feat: prove reviewed impact disposition - #7

Problem and scope

Follow-up to draft #6, stacked on Core draft #89. P2C4 extends the recorded official-public-data journey through an explicit governed feedback Decision.

The P2C3 structural criterion remains useful and its non-effective action remains promote. A separate authenticated and authorized World reviewer records reject with no_action because structural citation coverage does not establish citation correctness, general Brief quality, causality, human benefit, or live freshness. Neither judgment is rewritten and effective state does not change.

Product boundary and compatibility

This is source-checkout candidate evidence only. It adds an acceptance harness, tests, a narrow P2C3 state handoff, and work/audit/roadmap documentation. The shipped JSON Domain Pack, connector, 0.9.0 version, ace-core>=0.5.0,<0.6 dependency range, lockfile, and release records are unchanged.

The named World principal and role/grant express product review policy; they are not a universal biological-personhood claim. No proposal is applied and the Domain Pack gains no behavior or authority.

Evidence

• P2C3 + P2C4 focused journey: 4 passed
• Complete stacked World suite: 87 passed
• Federal Register connector: 26 passed
• Release contract: 7 passed
• Locked public-Core compatibility: 82 passed, 5 explicit candidate skips
• Ruff changed-file check and format: pass
• Unchanged 0.9.0 source/wheel build: pass; wheel remains inert/data-only
• git diff --check: pass

The audit freezes the exact evaluation, proposal, Decision identities, rationale, replay result, and non-claims.

Risk and rollback

Blast radius is the additive P2C4 harness/test and P2C3 acceptance-state handoff. Rollback removes those files and candidate documentation. Any Decision persisted by a host remains immutable audit history. There is no shipped-pack, schema, connector, or release artifact migration.

Checklist

• Public recorded fixtures only; no private data or credentials.
• Exact product/Core/Intelligence ownership boundaries are preserved.
• Focused, complete, connector, release, public-compatibility, lint, format, build, and diff gates ran.
• Documentation remains candidate-scoped and does not claim human benefit, causality, live freshness, effective promotion, SI4, or ACE 0.6 completion.
• No merge, tag, package publish, or release change is included.